'

\ufeffUsing the command prompt to answer the question

PART 5: CONFIGURING ETHERCHANNEL BETWEEN S1 \ufeffAND S2 \ufeffYou may have noticed that we have multiple links between S1 \ufeffand S2. \ufeffIf you look carefully at the Packet Tracer screen, you will see that only one of the two connections is active at a time. Furthermore, if you run the show spanning-tree command on the switch next to the amber light indicating the disabled link, you will see that the Spanning Tree Protocol disables the port and shows the port as Altn BLK. 

5.1 \ufeffImplement EtherChannel between S1 \ufeffand S2 \ufeffImplement EtherChannel between S1 \ufeffand S2 \ufeffas follows • \ufeffOn both switches, create Port-Channel group number 1 (one) \ufeffusing LACP and add both interfaces that interconnect the devices to the Port-Channel group • \ufeffOn S1, \ufeffenable LACP to actively try to establish EtherChannel with the device connected to the port • \ufeffOn S2, \ufeffenable LACP to establish EtherChannel only in response to an LACP packet received from the connected device • \ufeffConfigure interface descriptions on the EtherChannel interface to read “Connection between S1 \ufeffand S2 \ufeffusing Port-Channel 1” 

5.2 \ufeffPart 5 \ufeffSummary You would see that both network connections between S1 \ufeffand S2 \ufeffand now used (as indicated by the green triangles in Packet Tracer). \ufeff

PART 6: CONFIGURING SPANNING TREE PROTOCOL While Spanning Tree Protocol is enabled on the switches by default, there are things we can optimize to make it better: • \ufeffChange spanning-tree to the Rapid per VLAN STP mode • \ufeffEnabling PortFast allows edge ports to enter the spanning tree forwarding state immediately, bypassing the listening and learning states • \ufeffAnd PortFast BPDU guard prevents loops by moving a non trunking port into an errdisable state when a BPDU is received on that port. • \ufeffFinally, you will configure S1, \ufeffS2, \ufeffand S3 \ufeffas the primary and secondary STP root bridges for designated VLANs 

6.1 \ufeffChange Spanning Tree Protocol By default, the switch uses the Per-VLAN Spanning Tree protocol. Change spanning tree to the Per-VLAN Rapid STP mode. 

6.2 \ufeffConfigure PortFast and BPDU guard Configure the following Spanning Tree settings to optimize the network: • \ufeffEnable Portfast by default on all access ports on all three switches • \ufeffThis will improve connectivity time to computers wired to the network port; it is especially important if the network is using DHCP • \ufeffEnable bpdu guard by default on all Portfast ports • \ufeffThis will ensure that if someone connects a rogue switch to your network, the port will be put into err-disabled mode 

6.3 \ufeffConfigure STP switch priority Configure switch priority to ensure that S1, \ufeffS2, \ufeffand S3 \ufeffare elected as root bridges for specific VLANs during the Spanning Tree election process: If you look at the network topology, you will likely notice several drawbacks of our design: • \ufeffthat not all links are enabled (as indicated by an amber dot that shows a blocking port) • \ufeffuncontrolled root bridge allocation • \ufeffonly one bridge is the root for all VLANs • \ufeffthe other switches are idle • \ufeffsuboptimal election of a root bridge To address these issues, you will configure each switch as a primary root bridge for specific VLANs and a secondary root bridge for others, thus load-balancing this functionality and optimizing traffic paths. Configure spanning tree priority as per the table below: VLAN 10 \ufeffVLAN 20 \ufeffVLAN 99 \ufeffVLAN 999 \ufeffPrimary root S1 \ufeffS2 \ufeffS3 \ufeffS3 \ufeffSecondary root S2 \ufeffS1 \ufeffS1 \ufeffS2 \ufeffWhen configuring the device as a primary or secondary root, do not change the priority directly; instead, use the command that configures the switch as the primary/secondary root using keywords. 

6.4. \ufeffPart 6 \ufeffSummary You have completed the Spanning Tree configuration, and now your PCs will connect to the network faster after the cable is plugged into the device. All links should be passing traffic and load-balancing the VLANs.